PR Stack (Queue Instrumentation)

• feat(core): [Queue Instrumentation 1] Add enableQueueTracing option and messaging span data conventions #5250
• feat(samples): [Queue Instrumentation 2] Add Kafka to Spring Boot 3 sample app #5253
• feat(spring-jakarta): [Queue Instrumentation 3] Add Kafka producer instrumentation #5254
• feat(spring-jakarta): [Queue Instrumentation 4] Add Kafka consumer instrumentation #5255
• feat(spring-boot-jakarta): [Queue Instrumentation 5] Add Kafka queue auto-configuration #5259
• test(samples): [Queue Instrumentation 6] Add Kafka queue system tests #5260
• feat(samples): [Queue Instrumentation 7] Add Kafka to Spring Boot 3 OTel sample apps #5265
• fix(spring-boot-jakarta): [Queue Instrumentation 8] Disable Sentry Kafka spans when OTel is active #5274
• fix(spring-jakarta): [Queue Instrumentation 9] Clean up stale ThreadLocal context in Kafka consumer interceptor #5279
• fix(spring-jakarta): [Queue Instrumentation 10] Fork root scopes and skip when OTel is active in Kafka consumer #5280
• fix(spring-jakarta): [Queue Instrumentation 11] Guard entire span lifecycle in Kafka producer interceptor #5281
• fix(spring-jakarta): [Queue Instrumentation 12] Add Kafka retry count attribute #5282
• fix(spring-jakarta): [Queue Instrumentation 13] Align enqueue time with Python #5283
• ref(kafka): [Queue Instrumentation 14] Extract sentry-kafka module #5288
• feat(samples): [Queue Instrumentation 15] Add opt-in Kafka console e2e coverage #5289
• fix(test): [Queue Instrumentation 16] Enable Kafka profile in system runner #5291
• feat(kafka): [Queue Instrumentation 17] Add manual consumer tracing helper #5312
• ref(samples): [Queue Instrumentation 18] Move Kafka sources into queues.kafka package #5313
• ref(samples): [Queue Instrumentation 19] Drop Kafka auto-config exclude from Spring Boot samples #5314
• ref(kafka): [Queue Instrumentation 20] Log Kafka instrumentation failures #5315
• fix(kafka): [Queue Instrumentation 21] Preserve third-party baggage on Kafka producer records #5316
• test(spring-boot-jakarta): [Queue Instrumentation 22] Cover spring-kafka class-absence gate #5318

📜 Description

Remove spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.kafka.KafkaAutoConfiguration from the default application.properties and the corresponding empty override from application-kafka.properties in all three Spring Boot Jakarta samples (sentry-samples-spring-boot-jakarta, sentry-samples-spring-boot-jakarta-opentelemetry, sentry-samples-spring-boot-jakarta-opentelemetry-noagent).

No behavior change in default or kafka-profile runs.

💡 Motivation and Context

spring.autoconfigure.exclude is a single list property — profile-specific files replace it rather than merge. The existing setup worked for one queue profile but does not compose with additional transport profiles we plan to add next (e.g. rabbitmq):

# application.properties
spring.autoconfigure.exclude=KafkaAutoConfiguration,RabbitAutoConfiguration

# application-kafka.properties
spring.autoconfigure.exclude=       # clears everything → also re-enables Rabbit

# application-rabbitmq.properties
spring.autoconfigure.exclude=       # clears everything → also re-enables Kafka

Activating the kafka profile would unsilence RabbitAutoConfiguration and vice versa; --spring.profiles.active=kafka,rabbitmq becomes order-dependent rather than additive.

We can drop the exclude entirely because:

• KafkaConsumer and KafkaController already carry @Profile("kafka"), so no @KafkaListener container starts and no broker connection is attempted when the profile is inactive.
• KafkaAutoConfiguration still creates an unused KafkaTemplate bean in non-Kafka runs, which is harmless.
• Sentry's Kafka auto-config (SentryKafkaQueueConfiguration in SentryAutoConfiguration) is independently gated on @ConditionalOnProperty(name = "sentry.enable-queue-tracing", havingValue = "true"). That property is only set in application-kafka.properties, so Sentry instrumentation behavior is unchanged.

This makes the samples compose cleanly with future queue-transport profiles.

💚 How did you test it?

• ./gradlew :sentry-samples:sentry-samples-spring-boot-jakarta:compileJava :sentry-samples:sentry-samples-spring-boot-jakarta-opentelemetry:compileJava :sentry-samples:sentry-samples-spring-boot-jakarta-opentelemetry-noagent:compileJava — clean build.
• ./gradlew spotlessApply apiDump — clean.
• The existing KafkaQueueSystemTest already covers the kafka profile end-to-end.

📝 Checklist

• I added GH Issue ID & Linear ID
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.
• No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

Add a rabbitmq profile to the Spring Boot Jakarta samples so Kafka and Rabbit can coexist without auto-config exclusion conflicts.

#skip-changelog

⚠️ Merge this PR using a merge commit (not squash). Only the collection branch is squash-merged into main.